fix: ensure the end2end command has exited on interrupt #474
Conversation
It does this by checking whether it's exited or not, and if not, kills it. This ensures that the command doesn't keep running in the background or cause any other odd shell behaviors once `cargo-leptos` returns. Presumably resolves leptos-rs#387
|
It seems like this isn't killing the Leptos server that I tested this locally on my Axum project by installing cargo-leptos using cargo install cargo-leptos --git=https://github.com/ilyvion-contrib/cargo-leptos.git --branch=en2end-kill-cmd |
Did you/could you try running it with |
|
Actually, I think the server only keeps running when the tests fail. If I make them all succeed it seems to kill it. Note that cargo leptos doesn't seem to log it's logs based on RUST_LOG (I'd guess so you can use that for your app), you have to use |
That's a thought. I can look into that next I'm able. 👍 |
2 participants
It does this by checking whether it's exited or not, and if not, kills it. This ensures that the command doesn't keep running in the background or cause any other odd shell behaviors once
cargo-leptosreturns.Presumably resolves #387